Phenotype measurement systems and methods

ABSTRACT

An image acquisition and analysis system is disclosed. The system enables high throughput, objective analysis of microbial samples over days or weeks. The system may accommodate upwards of twelve 96- or 384-well plates simultaneously (liquid or solid media). The system may acquire and analyze a large number of samples in a short period of time. For example, over 384 samples per minute or 18,432 samples per hour. The system hardware may include a multi-spectral imager (fluorescence and bright field detection), electro-mechanical assemblies, and an optional high-resolution stage. The system may automate image acquisition, image data processing, simplify data storage, and enable automated analysis tools to significantly reduce the manual labor and time associated with such tasks. The system may allow for quick processing and analysis of data into clear phenotypic classes. The analysis capabilities may include colony growth, colorimetry, and structural morphology assays, and automated phenotype classification capabilities.

CROSS REFERENCE

This application claims the benefit of U.S. Provisional PatentApplication No. 62/467,011, filed Mar. 3, 2017, the entire disclosure ofwhich is incorporated by reference.

TECHNICAL FIELD

This disclosure is generally related to the detection and analysis ofphenotypes. More particularly, this disclosure is related to theautomated detection, analysis, and classification of phenotypes ofcellular assays.

BACKGROUND OF THE INVENTION

Current instrumentation for phenotype measurement is not keeping pacewith the scale in which modern microbiology and cell molecular biologyis performed. Quantitative methodologies are used to study cellularfunctions, the molecular mechanisms underlying specific phenotypes, andthe levels of RNAs, proteins, and metabolites. For example, insightsabout the virulence or drug resistance of pathogenic bacteria or fungicould be gained from quantitative growth dynamics and morphologicalanalyses of cellular colonies over extended periods of time (days toweeks). However, currently systems only provide for microbialresearchers to choose between highly accurate temporal resolutionexperiments on a relatively small number of strains or conditions, orsingle end-point data acquisition for a large number of strains orconditions. Furthermore, current systems fail to provide an efficientmeans of integrating the vast quantities of data produced among a groupof experiments or among the combined experiments of a group ofcollaborating researchers during data analysis.

SUMMARY OF THE INVENTION

An image acquisition and analysis system is disclosed. The systemenables high throughput, objective analysis of two-dimensional orthree-dimensional cell or colony cultures (including spheroid ororganoid cultures) of animal, plant, or microbial samples over days orweeks. The system may accommodate upwards of twelve single-well plates,96-well plates or 384-well plates simultaneously (liquid or solid media,including agar or other gel matrices). The system may acquire andanalyzing a large number of samples in a short period of time. Forexample, over 384 samples per minute or 18,432 samples per hour. Thesystem hardware may include a multi-spectral imager (fluorescence andbright field detection), electro-mechanical assemblies, system-level andsample-level environmental controls and monitoring, and an optionalhigh-resolution stage. The system may automate image acquisition, imagedata processing, simplify data storage, and enable automated analysistools to significantly reduce the manual labor and time associated withsuch tasks. The system may allow for quick processing and analysis ofdata into clear phenotypic classes. The analysis capabilities mayinclude colony growth, colorimetry, and structural morphology assays,and user-defined, supervised, or unsupervised automated phenotypeclassification capabilities.

In various aspects, the present disclosure provides methods and systemsfor the classification of one or more specimen. In some aspects, thepresent disclosure provides systems comprising a controller configuredto interface with one or more instrument through an instrument gatewaymodule configured to receive one or more experimental data set from theone or more instrument, wherein the one or more experimental data set isproduced during one or more experiment extract one or more feature dataset from the one or more experimental data set, store at least a portionof the one or more feature data set in a long-term data storagesubsystem, store at least a portion of the one or more feature data setor at least a portion of the one or more experimental data set in ashort-term storage cache, build one or more classification profile basedon a classification data set comprising at least a portion of the one ormore feature data set and classify one or more specimen of an experimentof the one or more experiment using the one or more classificationprofile.

In some aspects, the classification data set comprises at least aportion of each feature data set of a plurality of feature data sets,wherein a first portion of the each feature data set is produced from afirst experimental data set and a second portion of the each featuredata set is produced from a second experimental data set.

In some aspects of the present disclosure, the first experimental dataset comprises data from a different experiment of the one or moreexperiment than the data of the second experimental data set. In someaspects, the controller receives a plurality of experimental data setsfrom a plurality of experiments before the extracting is performed onany of the experimental data sets. In some aspects, the controllerreceives a plurality of experimental data sets from a plurality ofexperiments before the classifying is performed on any of theexperimental data sets. In some embodiments, at least a portion of thefirst experimental data set is received from a different instrument ofthe one or more instrument than the second experimental data set. Insome respects, the classification of one or more specimen comprisescategorizing the one or more specimen based on one or more feature dataset. In some aspects, building the classification profile comprisessupervised machine learning. In some aspects, building theclassification profile comprises unsupervised machine learning. In someaspects, the classification is performed in real-time, near real-time,or batch mode.

In some aspects of the present disclosure, classification results aredetermined from the classification of one or more specimen of anexperiment of the one or more experiment using the classificationprofile. In some aspects, the controller is further configured todisplay the classification results in real-time, near real-time, orbatch mode. In some aspects, the controller is further configured todisplay an analysis data set comprising at least a portion of theexperimental data set, at least a portion of the feature data set, or atleast a portion of the classification data set. In some aspects, theanalysis data set is displayed in real-time, near-real time, or batchmode.

In some embodiments of the present disclosure, the experimental data setcomprises image data. In some embodiments, the experimental data setcomprises a positive file format.

In some embodiments of the present disclosure, the controller is furtherconfigured to transmit an experiment design to the one or moreinstrument.

In some aspects of the present disclosure, the specimen comprises one ormore cell. In some aspects, a cell of the one or more cell comprises agenetically modified cell. In some aspects, the specimen comprises aplurality of cells. In some aspects, the plurality of cells comprises aheterogeneous mixture of cells. In some aspects, the plurality of cellscomprises one or more colony of cells.

In some embodiments of the present disclosure, an experiment of the oneor more experiments comprises an antibiotic screening assay, a drugscreening assay, a cellular growth assay, a colony growth assay, abio-prospecting assay, or an assay correlating molecular expression withfunctional activity.

In various aspects, the present disclosure provides methods for theclassification of one or more specimen, the methods comprising:receiving one or more experimental data set from one or more instrument,wherein the one or more experimental data set is produced during one ormore experiment; extracting one or more feature data set from the one ormore experimental data set; storing at least a portion of the one ormore feature data set in a long-term data storage subsystem; storing atleast a portion of the one or more feature data set or at least aportion of the one or more experimental data set in a short-term storagecache; building one or more classification profile based on aclassification data set comprising at least a portion of the one or morefeature data set; and classifying one or more specimen of an experimentof the one or more experiment using the one or more classificationprofile.

In some aspects, a plurality of experimental data sets is receivedbefore the extracting is performed on any of the experimental data setsof the plurality of experimental data sets. In some aspects, a pluralityof experimental data sets is received before the classifying isperformed on any of the experimental data sets of the plurality ofexperimental data sets. In some aspects, the classification of one ormore specimen comprises categorizing the one or more specimen based onone or more set of feature data. In some aspects, building theclassification profile comprises supervised machine learning. In someaspects, building the classification profile comprises unsupervisedmachine learning. In some aspects, the present disclosure providesmethods comprising displaying an analysis data set comprising at least aportion of the experimental data set, at least a portion of the featuredata set, or at least a portion of the classification data set. In somerespects, the classification results are displayed in real-time, nearreal-time, or batch mode. In some aspects, the present disclosureprovides methods further comprising displaying an analysis data setcomprising at least a portion of the experimental data set, at least aportion of the feature data set, or at least a portion of theclassification data set. In some aspects, the present disclosureprovides methods further comprising transmitting an experiment design tothe one or more instrument.

INCORPORATION BY REFERENCE

All publications, patents, and patent applications mentioned in thisspecification are herein incorporated by reference to the same extent asif each individual publication, patent, or patent application wasspecifically and individually indicated to be incorporated by reference.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the invention are set forth with particularity inthe appended claims. A better understanding of the features andadvantages of the present invention will be obtained by reference to thefollowing detailed description that sets forth illustrative embodiments,in which the principles of the invention are utilized, and theaccompanying drawings of which:

FIG. 1 shows a block diagram of a system for integrated high-throughputphenotypic analysis of cellular assay data and associated data flow inaccordance with one or more embodiments disclosed herein.

FIG. 2 shows a schematic diagram of a network for integratedhigh-throughput phenotypic analysis of cellular assay data in accordancewith one or more embodiments disclosed herein.

FIG. 3 shows a flow diagram of a method for coordinating integratedhigh-throughput acquisition and analysis of phenotypic cellular assaydata in accordance with one or more embodiments disclosed herein.

FIG. 4 shows a flow diagram of a method for the integrated operation ofan instrument in the high-throughput phenotypic analysis of cellularassay data in accordance with one or more embodiments disclosed herein.

FIG. 5 shows a flow diagram of a method for integrated high-throughputanalysis of phenotypic cellular assay data in accordance with one ormore embodiments disclosed herein.

FIG. 6 shows a flow diagram of a method for high-throughput analysis ofphenotypic cellular assay data involving integration of an additionaldata acquisition tool in accordance with one or more embodimentsdisclosed herein.

FIG. 7 shows a flow diagram of a method for integrated high-throughputanalysis of phenotypic assay data in accordance with one or moreembodiments disclosed herein.

DETAILED DESCRIPTION OF THE INVENTION

The systems, methods, and devices described herein can be used toautomatically and efficiently process experimental data from one or moreexperiment. In some embodiments, these systems, methods, and devices canbe configured to coordinate and perform analysis and classification ofmassive data sets received from a plurality of data acquisition tools.For example, the systems, methods, and devices described herein can beused to automatically extract a customizable set of aspects or featuresfrom imaging data acquired from a plurality of high-throughput dataacquisition tools, build an ontological classification profile based onfeatures extracted from massive quantities of raw data, and apply theclassification profile within or across data sets. Since a singleinstance of such analysis may use the functions or capabilities of aplurality of data acquisition tools (which can include one or more dataprocessing system such as one or more computational tools), the systems,methods, and devices described herein may accomplish analysis andclassification of a given data set by routing data to various modules,subsystems, or additional data acquisition tools.

The systems described herein may be used to analyze and/or classify dataoriginating from image acquisition systems such as systems comprising acamera or a microscope. For example, the systems, methods, and devicesdescribed herein are well-suited for analysis of imaging data producedduring growth and toxicity assays involving either prokaryotic oreukaryotic cells, including microbes (e.g., yeasts such as Saccharomycescerevisae, bacteria such as Escherichia coli, or mutant variantsthereof), mammalian cells, and other primary cells and cell lines (e.g.,cell lines with or without artificially modified genetic material). Forexample, the systems, methods, and devices can be used to analyze datacollected from cellular assays (e.g., colony growth or cellular toxicityassays involving yeast or bacteria) performed on liquid media substrates(e.g., liquid broth media such as YPD broth, wherein cellular specimensmay be pooled) or solid media substrates (e.g., solid agar substrates).In some embodiments, data sets that can be analyzed or classified usingthe systems, methods, and devices described herein can be derived from avariety of assays and experiments, including antibiotic, biomarker, anddrug screening assays, cellular growth assays, bio-prospecting assays(e.g., experiments pertaining to development of cellular strains forregenerative medicine, industrial biofuel production, agriculturalmicrobial products and crop modifications, or environmentalrehabilitation), molecular expression functional activity assays(colorimetric or fluorescent reporter molecules associated with enzyme,protein, RNA or metabolite production, such as antibody-linkedreporters, genetically expressed reporters, or cell-permeable ornon-cell-permeable dyes), morphologic behavior (structural assemblyvariation) and experiments pertaining to the identification and/orcharacterization of pathogenic or virulent cell types. Moreover, thesystems, methods, and devices allow for analysis (e.g., featureextraction, classification, and/or comparison) of experimental data forindividual experimental groups (e.g., a certain strain of yeast) acrossas many as 50, 100, 200, 500, 1000, 5000, 10000, or even 100000experiments (e.g., analysis stacking), which may comprise an extremelylarge number of experimental conditions in aggregate. In someembodiments, these analytical modalities can be repeated for eachexperimental group of a plurality of experimental groups, wherein theplurality of experimental groups can comprise 50, 100, 150, 200, 250,500, 1000, 2500, 5000, 7500, or 10000 different specimens (e.g., cellscomprising a different genetic modification or background).

The use of systems, methods, and devices described herein allows foridentification of phenotypic and functional characteristics fromanalysis of samples (e.g., individual genetic variants) on a scalenecessary for pharmacogenomic screening, quantitative trait mapping,synthetic biology, and systems biology approaches in both industrial andacademic settings. For example, one or more complex trait (e.g., whereinmultiple genes contribute to single phenotype) and/or one or morepleiotropic trait (e.g., wherein a single gene contributes to multiplephenotypes) can be identified or recognized in a specimen using thesystems, methods, and devices described herein. In some embodiments, oneor more correlation may be established between a set of experimentalconditions (e.g., genetic strain of a cellular specimen or treatmentconditions) and a set of one or more complex trait and/or one or morepleiotropic trait in a specimen. In some embodiments, advantagesconferred by the capabilities of the systems and methods describedherein (e.g., as a result of capacity for increased scale ofexperimental interrogation and data collection, highly controlledrepeatability, high sampling rate, prolonged duration of data setcollection, efficient data analysis, and/or statistical robustnessresulting from cumulative accrual of analytical assets). Theseadvantages allow for both analytical and predictive approaches toapplications such as understanding associations between genotype andphenotype, mapping complex molecular pathways, understanding structural,chemical, and electrical cell-to-cell interactions in three-dimensionalenvironments, and determining temporal expression patterns of RNA orproteins.

While described herein primarily in terms of analysis and classificationof image-based data acquired from cell-based assays, it is contemplatedthat the systems, methods, and devices described herein can be used toanalyze and classify virtually any data set. For example, the systemsand methods described herein can be useful in the analysis (e.g.,classification) of data sets produced or collected by non-imagingmodalities (e.g., data from an electrochemical detection assay receivedfrom an instrument or 3^(rd) party tool). In some embodiments, analysisof non-image-based data (e.g., data or metadata received from aninstrument, user, or 3^(rd) party tool) may be used to modify one ormore data set used by the system for analysis (e.g., a feature data set,a training data set, or classification data set).

FIG. 1 shows an embodiment of system 100, which can be useful inhigh-throughput phenotypic analysis of cellular assay data. System 100can include a plurality of components in communication with one another,for example, via a local network connection or a telecommunicationnetwork connection (e.g., a telecommunication network in communicationwith platform system 101). A component of system 100 can be a physicalcomponent (e.g., a user terminal 102 such as a computer or workstation,a data acquisition system 106, 108, a computational tool 104, a router,a server, a processor, a controller, a data storage medium, or anautomated device) or a virtual component (e.g., a software module 110,120, 130, 140, 150 or software subsystem thereof). In some embodiments,one or more first component of system 100 can control one or more secondcomponent of system 100, for example, through the transmission ofinstructions from the one or more first component to the one or moresecond component.

System 100 can comprise one or more user terminal 102, and one or moredata acquisition systems 106, 108 (e.g., instrument 106, 108) or one ormore computational tool 104. User terminal 102 can comprise a computer,a mobile device, or a workstation. User terminal 102 can be connected tosystem 100 by connection 103, which can be a wireless connection or aphysical connection (e.g., a wired connection which may or may notinvolve wireless components, such as a wireless router). A dataacquisition system can comprise an instrument 106, 108 (e.g., amicroscope, an experimental condition management system such as afluidics system or culture plate management system, an environmentcontrol system such as an incubator, an imaging system comprising adetector such as a camera and/or a source of radiation such as a laseror other illumination device).

One or more user terminal 102 may be connected to one or more additionaluser interface and/or to one or more data acquisition system by platformsystem 101. One or more user interface terminal 102 may also beconnected to one or more additional user interface and/or to one or moredata acquisition system via a local network connection.

System 100 can include integrated modules for division and/or completionof individual tasks. System 100 can comprise a platform system 101 thatcan include, for example, an application module 110, an instrumentgateway module 120, an analysis engine module 130, an interface module140, and a storage module 150. A subsystem or module of either system100 or platform system 101 may be connected to one or more subsystem ormodule of either system 100 or platform system 101, for example, tofacilitate efficient analysis of stored or acquired experimental data.Application module 110 can provide services and tools related to theuser interface for the system 100 for integrated high-throughputphenotypic analysis of cellular assay data. Application module 110 canreceive one or more client request from the user (e.g., via connection103) and route or transmit the client request to one or more module orsubsystem of system 100. In some embodiments, the application module 110can communicate information, such as settings, experimental results,analyzed data, and instructions for carrying out the high-throughputautomated phenotypic analysis of the cellular assay data, between asystem client (e.g., a user) and one or more module or subsystem ofsystem 100. For example, a system client may communicate an experimentdesign (e.g., input or transmit a client request) to experiment designsubsystem 112 of application module 110 via a connection 103 using userterminal 102. After being selected or defined by a client, anexperimental design can be communicated to an instrument for execution(e.g., via instrument gateway module 120) or to a subsystem comprisingmemory (e.g., storage module 150) for future use.

Experiment design subsystem 112 can be configured to provide tools to aclient useful in designing an assay (e.g., for execution by one or moredata acquisition system 106, 108). For instance, experiment designsubsystem 112 can allow a client to define one or more aspect (e.g., oneor more configuration parameter) of an experiment design, including oneor more configuration parameter for one or more data acquisition system108 (e.g., for communication to instrument gateway module 120), one ormore analysis method (e.g., for communication to analysis engine module130), one or more computational tool 104, or one or more additional dataacquisition tool 106 (e.g., for communication to interface module 140).

A configuration parameter can be an experimental variable. In someembodiments, a configuration parameter can be an environmental conditionor parameter, a treatment condition or parameter, a time parameter, acalibration parameter, an imaging method or condition, an image or dataanalysis method or algorithm, a detectable metric or feature, or aclassification profile or method. For instance, a configurationparameter can be a number of experimental or control groups orreplicates for an experiment, an experimental time point or endpoint, astatistical method, a threshold value (e.g., for image analysis, forstatistical stringency, or for maintenance of environmental conditions),or a definition of one or more instruments to be used to carry out anexperiment.

In some embodiments, a configuration parameter of an experiment designcan comprise one or more custom (e.g., user-defined) configurationparameter, one or more pre-defined (e.g., stored) configurationparameter, or a combination of one or more custom configurationparameter and one or more pre-defined configuration parameter. Apre-defined configuration parameter may be defined by a configuration orsoftware parameter of a data acquisition system, a configuration orparameter of stored data (e.g., a stored experimental design orclassification profile). In some embodiments, a custom configurationparameter may be defined by, limited by, or informed by an aspect of amodule or component with which the application module is incommunication. For example, a custom configuration parameter may bedefined by or limited by the capabilities or preset parameters of aninstrument or additional data acquisition tool selected for anexperiment or by the set of configuration parameters of a selectedstored experiment design (e.g., as communicated to application module110 by storage module 150), and it may be informed by actualenvironmental conditions detected in or around data acquisition system106, 108 (e.g., as communicated to application module 110 by instrumentgateway module 120).

Data visualization subsystem 114 can be configured to provide a userinterface for viewing, interpreting, and visualizing the data andanalysis results for an assay. Data visualization subsystem 114 can beused to present raw, partially processed, or fully processed data. Datapresented to a client of system 100 can be qualitative or quantitative.Data visualization subsystem 114 can present data according to presetvisualization profiles and functions or user-defined visualizationpreferences, which, in some embodiments, can each be selected prior to,during, or after the collection or presentation of experimental oranalyzed data (e.g., by user input via connection 103). Presetvisualization profiles and functions and user-defined visualizationpreferences can be stored in storage module 150. The format of datapresented via data visualization subsystem 114 can comprise graphs,tables, charts, image stacks, three-dimensional renderings, movies(e.g., movie data captured as such by an data acquisition system orstatic images stitched together after collection), or a combinationthereof.

In some embodiments, data can be presented via data visualizationsubsystem 114 in real-time or near real-time. For example, dataproduced, collected, or analyzed using a remote or local dataacquisition system or using an additional data acquisition tool 106 orcomputational tool 104 can be transmitted to data visualizationsubsystem 114 (e.g., via one or more module or subsystem of system 100)for immediate display. In some embodiments, data presented by datavisualization subsystem 114 can be refreshed or updated without lag(e.g., in real-time) or with minimal lag (e.g., near real-timepresentation, which can, in some embodiments, result from real-time dataanalysis performed by a module or subsystem of system 100). In someembodiments, data can be presented in batch mode, which can comprisedelaying the display of all or a portion of the collected or processeddata (e.g., so that the all or a portion of the data may be displayed atthe same time). Batch mode presentation or analysis of data may beadvantageous or necessary, for example, because it can allow for batchmode processing and can allow for low-cost processing and/or datastorage availability.

Data presented via data visualization subsystem 114 can compriseexperimental data (e.g., images captured during an experiment orpartially processed images), analyzed experimental data (e.g., dataresulting from quantitative or qualitative analysis of experimental datasuch as image data, feature data, graphs comprising raw data, processeddata, or metadata), classification data (e.g., one or moreclassification profiles, one or more feature data set, and/or one ormore experimental data set), classification results (e.g., as determinedfrom classification of an experimental group or specimen), experimentalcondition data (e.g., measured environmental data such as temperature,humidity, barometric pressure, atmospheric gas composition, and cameraor lighting settings), stored data, or metadata (such as time-basedmetrics like treatment or exposure durations and image captureintervals).

Data visualization subsystem 114 can be used to present imaging datarecorded during an experiment. Imaging data can comprise individualsample or whole-plate images, time-lapse image series (e.g., images froman experiment edited together and presented with movie playback orslider bar controls). Imaging data can be raw, partially processed, orfully processed.

Raw or analyzed data can be passed to data visualization subsystem 114from another module or subsystem of system 100. For example, raw datacan be transmitted from instrument gateway module 120 to datavisualization subsystem 114. In some embodiments, raw data can be passedfrom a subsystem of instrumentation gateway module 120, such as imageingest subsystem 122 or instrument monitoring subsystem 126. In someembodiments, data can be transmitted to data visualization subsystem 114from a subsystem of analysis engine module 130 (e.g., image processingsubsystem 132, feature extraction subsystem 134, or classificationsubsystem 136). Raw or analyzed data can also be passed to datavisualization subsystem 114 from storage module 150, and subsystemsthereof. Data can be transmitted to the data visualization subsystem 114from interface module 140 and subsystems thereof (e.g., after receiptfrom an additional data acquisition system 106). In some embodiments,data from experiment monitoring subsystem 116 of application module 110can be passed to data visualization subsystem 114.

Application module 110 can comprise experiment monitoring subsystem 116,which can be configured to provide status monitoring of the one or moredata acquisition system 106, 108 or computational tool 104, duringoperation of the one or more data acquisition system (e.g., during dataacquisition of a given assay). Experiment monitoring subsystem 116 canproduce or comprise a means for producing a user interface for displayof data or parameters relating to an experiment (e.g., a cellularassay).

For example, the status of a data acquisition system (e.g., aninstrument 108 or an additional data acquisition tool 106) orcomputational tool 104 may be passed to experiment monitoring subsystem116 by instrument gateway module or a subsystem thereof. For example, asensor of an data acquisition system (e.g., an instrument 108) candetect or measure one or more aspect of an experiment or of dataacquisition system 106, 108 (e.g., one or more environmental condition,experimental parameter, time-based condition, analysis parameter, devicestatus code, error code) and transmit the detected or measured data toexperiment monitoring subsystem 116. In some embodiments, experimentmonitoring subsystem 116 can comprise a memory or storage cache intowhich data can be stored (e.g., a short-term storage cache or buffer forcollection of experimental data to be displayed).

In some embodiments, data can be presented via experiment monitoringsubsystem 116 in real-time or near real-time. For example, datacollected or analyzed using a remote or local data acquisition system orusing an additional data acquisition tool 106 or computational tool 104can be transmitted to experiment monitoring subsystem 116 (e.g., via oneor more module or subsystem of system 100) for immediate display. Insome embodiments, data presented by experiment monitoring subsystem 116can be refreshed or updated without lag (e.g., in real-time) or withminimal lag (e.g., near real-time presentation, which can, in someembodiments, result from real-time data analysis performed by a moduleor subsystem of system 100). Experiment monitoring subsystem 116 canalso be operated in batch mode, which can comprise delaying thepresentation of all or a portion of the collected or processed data(e.g., so that the all or a portion of the data may be presented at thesame time).

In some embodiments, experiment monitoring subsystem 116 may present auser with unrequested information and may, optionally, prompt the userfor input (e.g., a client request). For example, if one or more statuscode or error message is received from one or more data acquisitionsystem 106, 108 or computational tool 104, experiment monitoringsubsystem 116 may present the one or more status code or error messageto the user. In some embodiments, experiment monitoring subsystem 116may present the user with a prompt to input preferences or commands(e.g., a client request) in response to the one or more status code orerror message (e.g., to be transmitted to the one or more dataacquisition system 106, 108 or computational tool 104). In someembodiments, a client request inputted by a user in response to a statuscode or error message may cause a modification or rectification of astatus (e.g., an operational error of a data acquisition system 106, 108or computational tool 104 or an experimental parameter).

Instrumentation gateway module 120 can provide an interface to one ormore instrument 108 and a means for communicating with the one or moreinstrument 108. Instrument gateway module 120 can transmit data (e.g.,instructions such as client requests) from one or more client (e.g.,user terminal 102, computational tool 104, or data acquisition system106, 108) to one or more instrument 108. Data (e.g., experimental data)transmitted from instrument gateway module 120 to a computational tool104, or data acquisition system 106, 108 can comprise experiment designinformation, setup or configuration instructions, status requests,instructions to initiate or terminate an operation (e.g., experimentinitiation or termination instructions), or data originating from othermodules, subsystems, instruments, or clients (e.g., an additional dataacquisition tool 106 or computational tool 104). Instrument gatewaymodule 120 may also receive any type of data from an instrument, module,or subsystem of system 100.

Instrument gateway module 120 and associated instruments and dataacquisition computational tools can be configured to acquire very largeexperimental data sets. For example, testing of this system has shownthat a high rate of sampling for collection of experimental data canyield unexpected levels of insight into the function and/or phenotype ofa specimen (e.g., as a result of more precise dissection of temporalevents and/or improved statistical resolution of subtle changes inquantifiable metrics); however, sampling at such a high rate can producequantities of data that other systems and methods are not able toreceive, analyze, classify, and/or store efficiently, if at all. In someembodiments, a high rate of sampling comprises sampling at less than thedoubling rate of a cellular specimen, less than half the doubling rateof a cellular specimen, less than one third the doubling rate of acellular specimen, less than one quarter the doubling rate of a cellularspecimen, or less than one eight the doubling rate of a cellularspecimen (e.g., when doubling rate is measured in a log phase ofcellular growth). In some embodiments, the doubling rate of a microbialspecies (e.g., bacteria, fungi, like yeast) can range from 10 minutes to45 minutes, from 15 minutes to 30 minutes, from 20 minutes to 25minutes, from 45 minutes to 60 minutes, from 60 minutes to 90 minutes,from 90 minutes to 180 minutes, from 90 minutes to 140 minutes, or from105 minutes to 120 minutes.

In some embodiments, instrument gateway module 120 may automaticallytransmit (e.g., without requiring user input) data received from anothermodule or client to one or more data acquisition system 106, 108 orcomputational tool 104. For example, during execution of an experimentaldesign requiring the coordinated function of two or more instruments,modules, and/or additional data acquisition tools, instrument gatewaymodule 120 may send data received from a first instrument or module ofsystem 100 to a second instrument or module of system 100 automatically.In some embodiments, data acquired from instrumentation gateway module120 can comprise an image ingest subsystem 122. Image ingest subsystem122 may be configured to accept data (e.g., experimental data) capturedby one or more data acquisition system 106, 108 during operation (e.g.,during execution of an assay of an experiment). In some embodiments,data received by image ingest subsystem 122 may include, but is notlimited to, images of plated cellular samples, environmental data (e.g.,parameters such as temperature, percent gas composition, and humidity),instrument settings (such as shutter speed, focal point, and duration ofexposure) and sample traceability data (such as barcoding, QR codes, orRFID), and sample plate calibration information (e.g., data relating toone or more of a dimension, feature, hue, saturation, contrast,intensity, or other colorimetry parameters of a sample). Image datapassed to image ingest subsystem 122 can be individual static images,grouped static images (e.g., image stacks), or movie files.

Instrumentation gateway module 120 can comprise instrument setupsubsystem 124, which can be configured to receive experimental datacomprising one or more configuration parameter. Instrument setup system124 can be configured to transmit a client request to data acquisitionsystem 106, 108 or computational tool 104 and/or to receive one or moreconfiguration parameter for an assay (e.g., one or more parameter of anexperiment design) from data acquisition system 106, 108. In someembodiments, a configuration parameter may be a capture interval, aplate configuration, a number of samples (e.g. a number culture platesor biological samples on a culture plate), an identification number(e.g., of an experiment or portion of an experiment such as a plate orregion of a plate), an imaging parameter (e.g., a setting related to afilter or image filtering method, a setting related to an illuminationsource, a setting related to signal detection such as selection of adetection method or specification of a gain level, intensity threshold,or contrast threshold), a start time, or a duration (e.g., a duration ofan experiment or capture event such as shutter speed of an imagingevent). In some embodiments, data may be received by image setupsubsystem 124 from experiment design subsystem 112 and transmitted toinstrument 108.

Instrumentation gateway module 120 can also comprise instrumentmonitoring subsystem 126. Instrument monitoring subsystem 126 can beconfigured to receive the instrument status data from one or moreinstrument 108. Instrument status data, which can comprise experimentaldata, can be transmitted from instrument monitoring subsystem 126 toanother module or subsystem of system 100. For example, instrumentmonitoring subsystem 126 may pass instrument status data from one ormore instrument 108 to experiment monitoring subsystem 116. In someembodiments, data transmitted or received by instrument monitoringsubsystem 126 can comprise instrument user/operator logs, experimentruntime logs, error logs, temporal environmental condition data (e.g.,relating to internal conditions of one or more instrument 108), servicehistory, hardware configuration information, and software configurationinformation.

Analysis engine module 130 can be configured to perform analysis ofexperimental data produced, stored, or received by one or more componentof system 100. For example, analysis engine module can be used toautomatically perform phenotypic classification of cellular samples ofan assay. In some embodiments, analysis engine module or a subsystemthereof may use data created or received by system 100 (e.g.,experimental data such as raw image data as well as or instead offeature data extracted from experimental data) to build a newclassification profile or to revise an existing classification profile.Analysis engine module 130 or a subsystem thereof may also apply aclassification profile (e.g., a stored classification profile or a newlycreated classification profile) to a data set (e.g., in order toclassify one or more experimental group, such as one or more specimen ofan experiment). Data useful for creation or revision of a classificationprofile can be raw data, partially processed data, or fully processeddata. In some embodiments data used by analysis engine module 130 can beextracted feature data and can comprise a feature data set.

Analysis engine module 130 can comprise image processing subsystem 132,which can be configured to pre-process images in preparation for featureextraction. Image processing subsystem 132 can apply one or more imageprocessing method to an input image stream received, for example, fromone or more of the instrument 106, 108. An image processing method canbe defined by and passed to analysis engine module 130 from storagemodule 150, a computational tool 104, an additional data acquisitiontool 106, or a user input (e.g., via a user terminal 102).

Image processing subsystem 132 can be configured to identify aspects ofan image (e.g., image features) and can, in some embodiments, apply oneor more modification to one or more image of the input image stream,such as filtering, thresholding, gray-scaling, Gaussian blur. In thisway, partial processing of one or more image of an image streamcollected by an instrument 106, 108 can be accomplished by imageprocessing subsystem 132. Whether pre-processing is performed by imageprocessing subsystem 132 and the combination and, if so, the degree towhich processing methods are applied by image processing subsystem 132can comprise a client request (e.g., comprising an experimental design)passed to analysis engine module 130 from application module 110 or anaspect of an experimental design stored in storage module 150 andselected by a user or used as a default method for a certainexperimental design. Image processing subsystem 132 can transmit one ormore raw or partially processed image of an image stream to featureextraction subsystem 134. In some embodiments, a partially processedimage can comprise data in a positive file format, such as TIFF or JPEGformatting.

In some embodiments, image processing subsystem 132 can receive andprocess a raw image sensor file (e.g., from an instrument 106, 108 orfrom storage module 150) or an image previously converted to a positivefile format (e.g., by instrument 106, 108, or by another module,subsystem, or component of system 100). For example, image processingsubsystem 132 can convert a raw image sensor file (e.g., raw image data)to a positive file format such as TIFF or JPEG before passing the datato another subsystem of the analysis engine module, such as featureextraction subsystem 134.

Feature extraction subsystem 134 can be configured to receive andprocess the data output of the image processing subsystem 132. Forexample, feature extraction subsystem 134 can receive one or more imageof an image stream from image processing subsystem 132 and can be usedto extract one or more feature from the one or more image. In someembodiments, feature extraction subsystem 134 can be used to measureimage features of a cellular sample. Feature data that can be extractedfrom collected and/or processed data (e.g., experimental data, such asimage data) can comprise one or more quantitative or qualitative aspectof an image. In some embodiments, a feature data set may comprise bothone or more quantitative aspect of an image and one or more qualitativeaspect of an image.

Feature data (e.g., image feature data) extracted by feature extractionsubsystem 134 may include, but are not limited to, object detection,object counting, circularity, statistical measurements of intensity andcolor channel (e.g., absolute intensity, hue, and/or saturationmeasurement or measurement of spatial changes in intensity, hue, and/orsaturation), edge detection, segmentation and segment counting, and/ordimensional measurement (e.g., length, thickness, area or diametermeasurement). In some cases, feature data may be extracted based whetherthe data meets or exceeds one or more threshold value. In someembodiments, feature data may comprise one or more feature determined orcalculated from one or more other feature data set (e.g., a relativemeasurement). For example, an object's height may be calculated from oneor more measurement of intensity and/or data comprising a position ofthe focal plane of the image. In some embodiments, feature extractionsubsystem 134 may comprise a method for identifying or quantifying acentroid of a cell or group of cells (e.g., a colony of cells, which cancomprise a plurality of cells that are physically associated orunassociated with one another), relative position of an object or groupof objects (e.g., with respect to the same object in a time course orwith respect to a second object, such as a cell, or group of objects,such as a colony of cells, at a given time point or over a time course),a method of using regions of interest (ROIs) or masked image data todetermine a boundary of an object (e.g., for determining differences incell or colony position or size) or group of cells (e.g., a colony ofcells), a method of determining the one or more dimension or quality ofa portion of an image (e.g., a determination of the length and/orthickness of a cellular filament or portion thereof), or a method oftexture segmentation (e.g., a method of determining cellular edgeruffling, halo features of a cell or colony, or ridged features of acell or colony).

Feature data can also comprise data determined or calculated bycomparing a plurality of data sets. In some embodiments, feature datacan be calculated or otherwise determined by comparing two or moreindividual frames of a video and/or two or more images in a temporalsequence of images, such as a time lapse image set. For example, colonygrowth rate can be determined by measuring and comparing a colonydiameter in two or more images of an experimental data set.

Feature extraction subsystem 134 can transmit processed (e.g., partiallyprocessed or fully processed) image data and/or extracted feature datafrom images of an image stream to the classification subsystem 136. Insome embodiments, feature extraction subsystem 134 can send data, whichmay include one or more extracted feature of one or more image of theimage stream, to the classification subsystem 136 without sending theimages themselves.

Analysis engine module 130 can comprise classification subsystem 136 forclassification of one or more data set and/or one or more experimentalgroup (e.g., one or more specimen of an experiment) based on raw,partially processed, and/or fully processed data (e.g., raw image files,extracted features, and/or data produced by additional data acquisitiontools). Classification of one or more data set and/or one or moreexperimental group (e.g., one or more specimen, such as a cell type) caninvolve assigning a functional or phenotypic label or categorization tothe data set or experimental group or categorizing the data set orexperimental group based on a functional or phenotypic trait of the dataset or experimental group (e.g., as determined by a comparison of thedata set or a data set related to the experimental group to one or moreadditional data set, such as a data set related to a differentexperimental group). Classification of one or more data set and/or oneor more experimental group can comprise applying a classificationprofile to a data set of an experiment or the compiled or aggregateddata from a plurality of data sets or experiments. In some embodiments,classification subsystem 136 can comprise grouping data sets orexperimental groups by a functional or phenotypic parameter (e.g., asdetermined from classification of experimental data). In someembodiments, classification subsystem 136 can comprise a memory orstorage cache into which data can be stored (e.g., a short-term storagecache or buffer for collection of experimental data to be displayed).

A classification profile can be built (e.g., created, compiled, revised,or modified) by comparing two or more data sets in which a relationshipbetween at least one aspect of each data set and at least one functionalor phenotypic aspect of the data set is known (e.g., in order to betterdefine the parameters governing the relationship between the at leastone aspect of the data set and the at least one functional or phenotypicaspect of the data set). In some embodiments, a classification profilecan be built by analysis engine module 130 or a subsystem thereof (e.g.,classification subsystem 136) using a machine learning algorithm. Insome embodiments, a classification profile can be built using a labeledtraining data set (e.g., supervised classification), and, in someembodiments, a classification profile can be built without using alabeled training data set (e.g., unsupervised classification). A labeledtraining data set can comprise a sample data set (e.g., comprisingexperimental data, calculated data, and/or data from another source suchas one or more scientific literature source) that bears an indication ofa feature, function, phenotype, classification, or other categorizationrepresented by at least a portion of the labeled training data set. Insome embodiments, a classification profile can be an interrogationfilter. In some embodiments, a classification profile can be inputted bya client of system 100 (e.g., via application module 110 or interfacemodule 140) and may be stored in a module or subsystem of system 100(e.g., storage module 150 or classification subsystem 136).

Classification subsystem 136 may apply a method of classification to adata set (e.g., a data set comprising one or more feature data set),depending, for example, on the configuration of the assay from which thedata being analyzed is derived. A method of classification can comprisea supervised method of classification or an unsupervised method ofclassification. A method of classification (e.g., a method of applying aclassification profile to a data set) can comprise dimensionalityreduction, one or more Monte Carlo-based technique (e.g., Monte Carlorandom sampling, Markov chain Monte Carlo, or Monte Carlo featureselection), clustering and anomaly detection, regression modeling,principal component analysis, linear discriminant analysis, binary,multi-class and linear classification based on labeled training data.

In some embodiments, a validation technique can be used to validate aclassification result. For example, cross-validation using standardmeasures such as accuracy and precision may be employed for validationof a classification result.

In some embodiments, classification subsystem 136 may use one or moreaspect of a data set (e.g., one or more raw image or portion thereofand/or one or more extracted feature such as a distance, a diameter, oran image contrast and complexity assessment) to determine one or morephenotypic or functional characteristic of the data set or of one ormore parameter producing the data set (e.g., an experimental group, suchas a cell type). In some embodiments, one or more relationship betweenan aspect of a data set and a phenotypic or functional characteristic(e.g., as determined by classification subsystem 136) can be stored in amemory-containing module of system 100 (e.g., a short-term storage cacheor a long-term data subsystem of one or more of storage module 150,analysis engine module 130, or classification subsystem 136). In someembodiments, one or more relationship between an aspect of a data setand a phenotypic or functional characteristic can be compiled into aclassification profile, which can be stored in a module or subsystem ofsystem 100 comprising memory.

In some embodiments, classification subsystem 136 may perform predictiveclassification of data as it is received by a module or subsystem ofsystem 100. In some embodiments, predictive classification can beperformed in real-time or near real-time as data is received byclassification subsystem 136. Predictive classification can comprise theuse of machine learning methods or algorithms.

Classification subsystem 136 can be configured to receive data fromimage processing subsystem 132, feature extraction subsystem 134,storage module 150, or a combination thereof, in conjunction with otherdata points gathered or used by instruments 106, 108, application module110, interface module 140, or instrumentation gateway module 120. Insome embodiments, data used by classification subsystem 136 can comprisemetadata, experiment design information, or configuration parameters.

Interface module 140, which may be a software-as-a-service (SaaS) APILayer, can be configured to provide a web services interface (e.g., aREST API) and/or one or more software development kit for one or moresoftware application or instrument to access, control, and interact withthe rest of the system 100. For example, may comprise a portal fortransmission of a client request (e.g., an experiment design or portionthereof or instructions to execute an experiment design) to a remoteadditional data acquisition tool. In some embodiments, interface module140 can comprise a software development kit useful in creating softwareto be used in interfacing with a computational tool 104 or an additionaldata acquisition tool 106 with system 100.

Interface module 140 can comprise image ingest API subsystem 142, whichcan be configured to provide for the integration of instrumentation ortools to access the image ingest subsystem 122. In some embodiments,image ingest API subsystem 142 can receive data (e.g., experimental datasuch as image data, extracted feature data, metadata, or data related toa classification profile or protocol) into system 100. For example,rules or routines comprising image ingest API subsystem 142 may be usedin the receiving of imaging data from an additional data acquisitiontool 106 (e.g., an instrument 106) and subsequently transmitting thedata to image ingest subsystem 122 (e.g., for further analysis orstorage in one or more module or subsystem of system 100). In someembodiments, software or firmware may be received by platform system 101from one or more additional data acquisition tool 106 or computationaltool 104 via image ingest API subsystem 142.

Interface module 140 can comprise analysis API subsystem 144, which canbe configured to provide a means of integrating one or morecomputational tool 104 and/or one or more additional data acquisitiontool 106 with analysis module 130 (e.g., feature extraction subsystem134 and/or classification subsystem 136). In some embodiments, analysisAPI subsystem 144 can transmit data received from one or morecomputational tool 104 or additional data acquisition tool 106 (e.g.,via image ingest API subsystem 142) to another module or subsystem ofsystem 100. For example, analysis API subsystem 144 can communicate datacreated or processed by computational tool 104 or by an additional dataacquisition tool 106 and received by image ingest API subsystem 142 toimage processing subsystem 132, feature extraction subsystem 134, orclassification subsystem 136.

Interface module 140 can also comprise storage API subsystem 146, whichcan be configured to communicate data from storage module 150 to one ormore computational tool 104 or additional data acquisition tool 106, orvice versa. For example, data produced by a computational tool 104 or anadditional data acquisition tool 106 may be downloaded to system 100 viastorage API subsystem 146. In some embodiments, stored data may beexported to one or more computational tool 104 or one or more additionaldata acquisition tool 106 via storage API subsystem 146. For example,experiment design or experiment metadata may be received from experimentdefinition subsystem 152 or experiment metadata subsystem 154,respectively, and transmitted to one or more computational tool 104 orone or more additional data acquisition tool 106 (e.g., in order for anexperiment to be carried out using one or more additional dataacquisition tool). In some embodiments, data used by one or morecomputational tool 104 or one or more additional data acquisition tool106 may be transmitted from storage module 150 (or a subsystem thereof,such as long-term image store subsystem 158) via storage API subsystem146.

In some embodiments, a plurality of subsystems of interface module 140may be used to communicate data between system 100 and one or morecomputational tool 104 or one or more additional data acquisition tool106 for the purpose of data analysis and/or classification. For example,analysis API subsystem 144 and/or storage API subsystem 146 may be usedto access image processing methods or algorithm libraries, visualizationtools, or sample metadata for data classification.

In some embodiments, a plurality of subsystems of interface module 140may be used to communicate data (e.g., download data to system 100 orexport data to one or more computational tool 104 or one or moreadditional data acquisition tool 106) for the purpose of allowing ancomputational tool 104 or an additional data acquisition tool 106 toaccess the data, methods, algorithms, functions, or protocols of one ormore module or subsystem of system 100. For example, an additional dataacquisition tool 106 may transmit image data to system 100 via imageingest API subsystem 142 to be transmitted to analysis engine module 130by analysis API subsystem 144 for analysis and subsequent export throughinterface module 140 or data storage in storage module 150.

Storage module 150 can comprise subsystems and methods for persistentstorage and data management. Storage module 150 and subsystems thereofmay receive data directly from or transmit data directly to any othermodule of system 100. Data stored in storage module 150 can comprise rawdata, partially processed data, or fully processed data. For example,data stored in storage module 150 can include raw image data, extractedfeature data, classification profile data, metadata, experiment designdata, user profile or login data, interface data, or any other type ofdata described or implied herein.

Storage module 150 may include experiment definition subsystem 152,which can be configured to maintain the data associated with theexecution of experimental assays and protocols. Experiment definitionsubsystem 152 may be used to store pre-defined methods and protocols forone or more assay, which can comprise an experiment design. Experimentdefinition subsystem 152 can also comprise custom (e.g., user defined)methods and protocols for one or more assay, which can also comprise anexperimental design. Data stored in experiment definition subsystem 152can be transmitted to instrument gateway module 120 or interface module140 to define settings and/or to control or instruct one or more dataacquisition system 106, 108 or computational tool 104 or communicationstherewith.

Storage module 150 can comprise experiment metadata subsystem 154, whichcan maintain intermediate and final data (e.g., partially or fullyprocessed data) received from analysis module 130. Data stored inexperiment metadata subsystem 154 can be transmitted to other modulesand subsystems of system 100 in order to fulfill various functions. Forexample, data stored in experiment metadata subsystem 154 can betransmitted to classification subsystem 136 for data classification orto data visualization subsystem 114 for display. In some embodiments,data stored in experiment metadata subsystem 154 can be made availableto one or more computational tool 104 or one or more additional dataacquisition tool 106 via interface module 140 (e.g., for further dataprocessing).

Image cache subsystem 156 of storage module 150 can comprise memory formaintaining data (e.g., image data) received from one or more dataacquisition system 106, 108. In some embodiments, data maintained byimage cache subsystem 156 can be transmitted to analysis module 130 forprocessing or classification. The image cache subsystem 156 may maintainthe image data at a quality suitable for visualization by theapplication module 110. In some embodiments, data in image cachesubsystem 156 can be maintained in more than one availability state,wherein an availability state can comprise image data having formattingor resolution conducive to instant, near-instant, or delayed processing,analysis, or visualization. In some embodiments, it is possible to moreefficiently supply image data to one or more other module or subsystemof system 100 by maintaining image data in a plurality of availabilitystates, depending on whether batch, near-real-time, or real-timeprocessing, analysis, or visualization is used for a given clientrequest or system function, which can, in turn, be determined at leastin part by processing cost and/or storage availability.

Long term image store subsystem 158 of storage module 150 can beconfigured to maintain (e.g., store) image data acquired by dataacquisition platform 106, 108 at a quality suitable for processing in anarchived format (e.g., for long-term and/or low-cost storage).

Instrument cache subsystem 159 of storage module 150 can be configuredto maintain data and information associated with a data acquisitionsystem interface, such as an instrument configuration. Data receivedfrom instrument gateway module 120 or a subsystem thereof, which caninclude any processed or utilized by instrument setup subsystem 124 orinstrument monitoring subsystem 126, can be stored in instrument cachesubsystem 159. Data stored in storage module 150 or a subsystem thereof(e.g., instrument cache subsystem 159) can be transmitted by storagemodule 150 or the subsystem thereof to analysis engine module 130 or asubsystem thereof (e.g., image processing subsystem 132, featureextraction subsystem 134, or classification subsystem 136) for analysis,which can include classification.

Referring now to FIG. 2, system 200 can comprise a plurality ofconnections to a plurality of clients, where a client can comprise adevice of system 200. Clients connected to integrated platform 201 caninclude individual user terminals, locally networked user terminals,individual instruments, locally networked instruments, additional dataacquisition tools, and additional data processing tools such ascomputational tools. In some embodiments, a first and second instrument106, 108 may be a first plurality of instruments and a second pluralityof instruments, respectively. In some embodiments, system 200 can be anembodiment of system 100, and integrated platform 201 can be anembodiment of platform system 101. Integrated platform 201 (and, thus,platform system 101 as well) may comprise one or more server 202, one ormore memory 204, and one or more processor 206 or controller. Modules,subsystems, or any function thereof may be coordinated, controlled, orexecuted by a controller or processor 206.

In some embodiments, a first portion of platform system 101 orintegrated platform 201 (e.g., a first group comprising one or moremodule or subsystem as described herein) can be executed in a differentcomputing environment than a second portion of platform system 101 orintegrated platform 201 (e.g., a second group comprising one or moremodule or subsystem, as described herein). A computing environment forexecuting the functions of a first or second portion of platform system101 or integrated platform 201 may comprise a client of system 100 orsystem 200. For example, a first portion of data used in the systems andmethods described herein (e.g., experimental data, feature data,metadata, classification data, classification profile(s), classificationresults, image data, partially- or fully-processed data, or stored data)can reside permanently or temporarily in a different computingenvironment than a second portion of data used in the systems or methodsdescribed herein. In some embodiments, an encryption key may be employedby the computing environment or may be assigned to a portion of the dataitself (e.g., cumulative cryptographic hashes).

A client (e.g., a user terminal 102, computational tool 104, or a dataacquisition system 106, 108) may be connected directly to a module ofintegrated platform 201 (e.g., application module 110 or interfacemodule 140), to one or more additional client (e.g., either locally orremotely). In some embodiments, a client can be connected to integratedplatform 201 directly and to one or more additional client through theconnection each client shares with integrated platform 201. In someembodiments, the access to one or more additional client granted to afirst client can be determined by a module or subsystem of integratedplatform 201. In some embodiments, such access can be granted to a firstclient for a limited period of time. In some embodiments, such accesscan be granted for compensation, such as a fee or mutual access grantedto the one or more additional client. In some embodiments, a client canbe assigned to a workgroup according to the customer and/or functionwith which the client is associated. A workgroup of system 200 cancomprise one or more client. For example, a workgroup can comprise oneor more user terminal 102 and/or one or more data acquisition system(e.g., one or more instrument and/or one or more additional dataacquisition tool).

An instrument of system 100 can comprise any means of performing,measuring, detecting, or quantifying an aspect of an experiment orassay. For example, system 100 can comprise one or more instrument 106,108, which can be a portion of a data acquisition system or anadditional data acquisition tool. In some embodiments, instrument 106,108 can comprise an image capture system, which can comprise one or moreinfrared light, visible light, fluorescent light or ultraviolet lightdetector (e.g., a photomultiplier tube or camera such as a digitalcamera capable of recording still images or video images), or amicroscope. An instrument 106, 108 can also comprise a light source(e.g., an ultraviolet light source, an infrared light source, a laserlight source, or a visible light source, which can comprise one or moreconfiguration for enhancing contrast such as phase contrast,differential interference contrast, bright field, dark field, Hoffmanmodulation, or polarized light techniques) or a source of electrical ormagnetic stimulation. In some embodiments, an instrument 106, 108 cancomprise a mechanism for moving all or a portion of an image capturesystem, such as a motor, a two-dimensional or three-dimensional gantry,and/or a lens focusing system. An imaging system can be operatedaccording to an imaging method, which can be, can depend upon, or can belimited by an experiment design.

In some embodiments, an imaging system of instrument 106, 108, such as amotorized camera system, can be automated. For example, the imagingmethod with which or order in which one or more sample (e.g., one ormore plate comprising one or more specimen or colony of specimens) isassayed (e.g., imaged) can be automatically determined and/or controlledby one or more module or subsystem of system 100.

In some embodiments, instrument 106, 108 can comprise or be operated ina controlled environment. For example, instrument 106, 108 can compriseone or more of a temperature gauge (e.g., a thermometer), ahumidification mechanism (e.g., a humidity pan, a humidificationchamber, or a microhumidifier), a humidity sensor, a source of a gas(e.g., carbon dioxide, oxygen, nitrogen, methane or any combinationthereof such as 5%, 10%, or 50% carbon dioxide in nitrogen, 5% or 10%carbon dioxide and 5% or 10% oxygen in nitrogen, or 10% oxygen innitrogen), a gas concentration measurement system (e.g., a gasanalyzer), or a heating source (e.g., an electrical heat source orwater-insulated heating jacket). In some embodiments, instrument 106,108 can comprise a spectroscope (e.g., ultraviolet-visible spectroscope,near-infrared spectroscope, X-ray chromatography equipment, atomicemission chromatography equipment, or a mass spectrometer such asLC-MS-MS), gas chromatography system, or a liquid chromatography system(such as high-performance liquid chromatography). In some embodiments,an instrument can comprise an environment at 0, 1, 2, 3, 4, 5, 6, 10,15, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36,37, 38, 39, 40, 45, 50, 55, 60, 65, 70, 71, 72, 75, 80, 85, 90, 95, or100 degrees Celsius, and an experiment or assay, as described herein,can be performed at 0, 1, 2, 3, 4, 5, 6, 10, 15, 20, 21, 22, 23, 24, 25,26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 45, 50, 55,60, 65, 70, 71, 72, 75, 80, 85, 90, 95, or 100 degrees Celsius. Forexample, microbial growth assays can be performed at 37 degrees Celsius.

Instrument 106, 108 can also comprise a system for moving a samplebefore, during, or after an experiment. For example, instrument 106, 108can comprise a sample handling system, which can comprise a cultureplate management system and/or a fluidic system. A plate managementsystem can comprise a plurality of culture plates or trays, which caneach comprise 1, 2, 3, 4, 6, 12, 24, 48, 96, or 384 wells. In someembodiments, a plate management system can comprise a tray or platestacker, a tray or plate selector, a tray or plate positioner, and/or amoveable microscope stage. In some embodiments, an instrument 106, 108can be capable of capturing image data from at least one, at least two,at least three, at least four, at least five, at least six, at leastseven, at least eight, at least nine, at least ten, at least eleven, orat least twelve single-well plates, 96-well plates or 384-well platessimultaneously.

In some embodiments, a sample management system of instrument 106, 108,such as a plate management system, can be automated. For example, theorder in which one or more sample (e.g., one or more plate comprisingone or more specimen or colony of specimens) is assayed (e.g., imaged)can be automatically determined and/or controlled by one or more moduleor subsystem of system 100.

In some embodiments, one or more aspect of instrument 106, 108 can becontrolled by a module or subsystem of system 100. In some embodiments,one or more aspect of instrument 106, 108 can be operated automatically.One or more instrument 106, 108 of system 100 can be operated locally orremotely using instructions received from platform system 101. In someembodiments, a user can specify one or more measurement, statisticalcomparison, assay, experiment, or series of experiments to be performedusing one or more specimen, and platform system 101 can automaticallypartition tasks, select equipment (e.g., one or more instrument 106, 108based on instrument availability and/or capability) to perform thetasks, transmit instructions (e.g., an experiment design) to one or moreinstrument for obtaining the user-requested one or more measurement,comparison, assay, experiment, or series of experiments.

In some embodiments, system 100 can comprise one or more computationaltool 104 or one or more additional data acquisition tool 106 with whichsystem 100 communicates through an interface module. In someembodiments, an additional data acquisition tool can comprise aninstrument 106 (e.g., additional data acquisition tool 106). In someembodiments, additional data acquisition tool can comprise a dataprocessing tool (e.g., a computational tool 104 or computationalplatform). A data processing tool, which can, for example, comprise acomputational tool 104, can comprise an analysis platform, such as acomputational biology platform. In some embodiments, data transmitted toinstrument 106 or data processing tool (e.g., computational tool 104)can undergo analysis (e.g., partially or fully processing orclassification). Optionally, data analyzed by an instrument 106 orcomputational tool 104 can be received by platform system 101 (e.g., asubsystem of interface module 140) after analysis by the instrument ordata processing tool. For example, one or more experimental data set,feature data set, and/or classification data set can be transmitted to acomputational tool 104 where it can be analyzed and/or wherecomputational tool 104 may build a classification profile, which can bereceived from computational tool 104 by interface module 140 or asubsystem thereof.

Referring now to FIG. 3, process 300 represents an example of how aclient (such as a user at a user terminal 102) may access allfunctionalities of system 100, as described herein. For instance, system100 may receive and may validate login information from the client in astep 302. In some embodiments, a client can be a local area networkaccount, which can be connected to one or more user terminal 102, one ormore computational tool 104, and/or one or more data acquisition system106. The client can be synchronized with a server of system 100 in astep 304. Synchronization of a client with a server of system 100 maycomprise transmitting and/or receiving updated data, software, orfirmware from the client to the platform system 101. In a step 306, theclient may be assigned to a workgroup, which may or may not comprise oneor more additional client. If the workgroup to which the client isassociated also comprises one or more additional client, the client maybe synchronized with all or a portion of the additional client(s) in theworkgroup via system 100 in a step 308. In some embodiments, a workgroupcan comprise one or more of a user terminal, a data acquisition system108, a computational tool 104, and/or additional data acquisition system106. A first client of a workgroup may be local or remote with respectto a second client of a workgroup and may or may not allow access to thesecond client of the workgroup (e.g., for the purpose of sharing data,experimental resources, or computational resources) and may or may notrequire compensation for said access.

After the client has been assigned to a workgroup and optionallysynchronized with one or more additional client of the workgroup, datamay be presented to the client in a step 310 reflecting updateinformation pertaining to input options, ongoing or completedexperiments, or stored data (e.g., via any of the subsystems ofapplication module 110). At step 320, the client may input a clientrequest to application module 110, which can be transmitted toinstrument gateway module 120 (e.g., in a step 340), analysis module 130(e.g., as in a step 350), interface module 140 (as in a step 360),and/or storage module 150 (e.g., as in a step 330). A client request cancomprise one or more command (e.g., instructions to display at least aportion of a data set, instructions to operate a data acquisitionsystem, instructions to create, edit, or delete data or to retrieve datafrom long-term or short-term storage, or instructions to perform one ormore method of data analysis such as applying one or more classificationprofile to a data set) or one or more data set (e.g., wherein a data setcan comprise experimental data, feature data, classification data, oneor more classification profile, metadata, one or more aspect of anexperimental design, or training set data). Commands (e.g.,instructions) contained in the client request can be carried out by themodules and subsystems of system 100 automatically. For example, aclient request may specify a plurality of assays be performed on aplurality of specimens and that one or more feature data set beextracted from the resulting experimental data set before one or moreclassification profiles is applied to the feature data set and thatclassification results be displayed in real-time, and platform system101 can automatically task one or more data acquisition systems (e.g.,via instrument gateway module 120 or via interface module 140, as insteps 340 and 360, respectively), request previously storedclassification data be transmitted from storage module 150 to analysisengine module 130 (e.g., as in a step 330), and/or instruct analysisengine module 130 to execute one or more feature extraction orclassification method on data received in analysis engine module 130from instrument gateway module 120 or interface module 140 (e.g., as ina step 350). At step 332, 342, 352, and 362, data may be returned (e.g.,received) from the instrumentation gateway module 120, analysis module130, interface module 140, and/or storage module 150 for display viaapplication module 110 (e.g., in batch mode display, in near-real-timedisplay, or in real-time display). The system can accept additionalclient requests prior to, during, or after display of returned data instep 310.

In some cases, client requests may be stacked. For example, a pluralityof client requests, which may or may not be interrelated with respect todata set, experiment, or data acquisition system, can be inputted by auser (e.g., via application module 110) and stored in a short-term orlong-term memory of system 100 (e.g., in storage module 150, a memory ofinstrument gateway module 120, a memory of analysis engine module 130, amemory of interface module 140, or a memory of a client, such as a userterminal or data acquisition system). In some embodiments, system 100may transmit or execute a client request from a plurality of differentclients at the same time. For example, system 100 may transmit clientrequests from a plurality of clients to the single instrument to beexecuted together or sequentially (e.g., if the client requests eachcomprise one or more similar aspect such as a similar experimentdesign), regardless of when the client requests were received from theclient, whether the client requests pertain to the same experiment, orwhether the client requests will produce or use the same data set(s) inwhen the data set(s) are collected/produced, analyzed, or displayed. Byregulating and grouping or batching a plurality of client requests orone or more portion of a plurality of client requests, it is possible toincrease computational efficiency and efficiency of data acquisitionsystem usage.

Turning now to FIG. 4, process 400 represents embodiments of theoperation of system 100 wherein an instrument (e.g., a data acquisitionsystem) is utilized in the creation of a data set. In a step 410, theinstrument may be connected to system 100, and system 100 may initiatean instrument setup protocol in a step 420. During instrument setup,data may be transmitted from instrument set-up subsystem 124 to theinstrument and/or data may be received from the instrument by instrumentset-up subsystem 124. Data transmitted or received during a step 420 maycomprise an environmental condition or parameter and/or instrumentstatus information, which can include, for example, one or moreinstrument error message or information pertaining to instrumentavailability and scheduling). Instructions regarding experiment designmay be received by experiment gateway module 120 from the applicationmodule 110 or from storage module 150 in a step 430 (e.g., as part of aclient request or as automatically selected by system 100 as the resultof a selection or preference indicated in a client request such as theselection of one or more specific type of analyzed data to be collectedfrom a specific set of specimens) and may be transmitted to theinstrument at a step 440. Transmission of one or more experimentaldesign to the instrument may be accompanied by or followed byinstructions to execute the experiment design and collect one or moredata set (e.g., experimental data). In a step 450, data may be receivedfrom the instrument by a subsystem of gateway module 120. For example,image data (e.g., as part of an experimental data set) may be receivedby image ingest subsystem 122, and data related to the status of thedata stream or the status of the instrument may be received byinstrument monitoring subsystem 126. Received data (e.g., rawexperimental data) may be transmitted to application module 110 fordisplay in real-time, near real-time, or batch mode in a step 460. Datamay also or may instead be transmitted to storage module 150, interfacemodule 140, analysis engine module 130, or any combination thereof(e.g., for storage, transmission to a computational tool 104 or anadditional data acquisition tool 106, or analysis).

In some embodiments, data received by instrument gateway module 120 canbe stored in both short-term and long-term memory. For example, rawimage data received from an instrument may be transmitted to ashort-term memory cache to be displayed with extracted features and/orclassification data after one or more analysis task has been completed,and it may also be transmitted to a long-term memory for long-term(e.g., cold) storage (e.g., storage module 150). In some embodiments,the data stored in a short-term cache may be of high, intermediate, orlow quality or resolution in order to reduce the amount of memoryrequired. In some embodiments, data may be transmitted to and stored ina long-term storage memory in its highest resolution and/or quality.

Referring now to FIG. 5, process 500 may be performed by system 100 forthe purpose of analyzing data collected or stored by system 100. Asdescribed herein, analysis of data, which can comprise featureextraction and/or classification, can be performed in real-time, nearreal-time, or batch mode. Analysis of data in batch mode may beadvantageous or necessary, for example, because batch mode processingcan reduce the computational cost of analysis. Experimental data can bereceived by analysis engine module 130 (e.g., in image processingsubsystem 132) from instrument gateway module 120 (e.g., from imageingest subsystem 122) in a step 502. Stored data to be analyzed can bereceived from storage module 150 (e.g., from image cache subsystem 156)in a step 504. Feature data (e.g., data comprising a feature data set)can be extracted from data received in step 502 or 504 by featureextraction subsystem 134 at a step 510. Extracted feature data may betransmitted to application module 110 for display or storage module 150for storage in steps 520 and 530, respectively. Extracted feature datamay be compiled into one or more classification data set and may be usedby classification subsystem 136 to build (e.g., create, compile, ormodify) a classification profile in a step 540. Classification dataand/or extracted feature data may be received from application module110, interface module 140 (e.g., as transmitted to the interface moduleor a subsystem thereof by a computational tool 104 or additional dataacquisition tool 106), and/or storage module 150 in step 550 for thepurpose of building a classification profile as well. In someembodiments, classification data transmitted in step 550 may beaccompanied by a set of training data (e.g., in order to build one ormore classification profile, as in step 540). A classification profilemay optionally be transmitted to application module 110, interfacemodule 140, or storage module 150 in a step 560. In some embodiments,building of a classification profile is unnecessary (e.g., when anexisting classification profile is selected or supplied by the user),and one or more of steps 540, 550, or 560 may be omitted from process500. Building a classification profile, as in a step 540, can comprisemodifying an existing classification profile, which can comprise addingto, modifying, or deleting data from one or more classification data setfrom which the classification profile was originally built. In someembodiments, newly extracted feature data may be incorporated into oneor more classification data set by analysis engine module 130 or asubsystem thereof. In a step 570, a data set (e.g., a feature data set)can undergo classification analysis wherein one or more functional orphenotypic characteristic may be ascribed to or associated with a dataset or experimental group. In some embodiments, data pertaining to oneor more functional or phenotypic characteristic of a data set orexperimental group can comprise a classification result. Aclassification result can be produced by the application of one or moreclassification profile, which can, in turn, comprise user-definedclassification data and/or classification data produced by supervised orunsupervised machine learning techniques. In a step 580, analyzed data,which may comprise a portion of a classification data set and/or one ormore classification result, can be transmitted to application module 110and/or storage module 150.

FIG. 6 illustrates an embodiment of process 600 wherein data istransferred between platform system 101 and a computational tool 104 oran additional data acquisition tool 106 via interface module 140. In astep 610, a connection can be established between platform system 101and the additional data acquisition tool 106 or computational tool 104.The computational tool 104 or additional data acquisition tool 106 canbe synchronized with interface module 140 at step 620. Synchronizationof the additional data acquisition tool with interface module 140 atstep 620 may comprise transmission of data from the computational tool104 or additional data acquisition tool 106 to storage API subsystem 146or vice versa. A client request may be received at step 630, forexample, instructing an experiment comprising one or more imaging eventto be performed using an additional data acquisition tool 106 orinstructing one or more computational tool 104 or one or more additionaldata acquisition tool 106 to perform a data analysis procedure. In anoptional step 640, additional data may be received by interface modulefrom another module or subsystem of platform system 101 concurrently orfollowing step 630. Data and/or a client request can be transmitted toone or more computational tool 104 or one or more additional dataacquisition tool 106 in a step 650. In a step 660, data can be receivedfrom one or more computational tool 104 or one or more additional dataacquisition tool 106 by one or more of the subsystems of interfacemodule 140, depending on what data is transmitted. At step 670, data maybe transmitted to application module 110 for display, instrument gatewaymodule for image ingest, analysis engine module 130 for featureextraction and/or classification, and/or storage module 150 for storage.

Referring now to FIG. 7, process 700 illustrates an embodiment of theoperation of system 100, wherein experimental data is acquired,analyzed, and displayed. In a step 710, a client request can be receivedfrom application module 110 (e.g., from user terminal 102). The clientrequest can be transmitted to instrument gateway module 120 in a step720, which can, in some embodiments, include transmission of anexperiment design from application module 110 to instrument gatewaymodule 120 as well. In a step 730, the data passed to instrument gatewaymodule 120 can be transmitted to an instrument. In some embodiments, theinstrument to which data is transmitted in step 730 is a computationaltool 104 or an additional data acquisition tool 106, in which case datatransmission may be routed through interface module 140, and in someembodiments, the instrument is not a computational tool 104 or anadditional data acquisition tool 106. In step 740, experimental data,such as image data, can be received by instrument gateway module 120. Ifone or more instrument with which the experimental data was produced isan additional data acquisition tool 106, a portion of the data may berouted to instrument gateway module 120 via interface module 140. In astep 750, experimental data may be transmitted to storage module 150 forstorage. In a step 760, the experimental data can be transmitted toapplication module 110 for display (e.g., in real-time, near real-time,or batch display mode). Experimental data can also be transmitted toanalysis engine module 130 for analysis (e.g., feature extraction and/orclassification) in a step 770. Optionally, experimental data can betransmitted to interface module 140 in step 780 for transmission to acomputational tool 104 or an additional data acquisition tool 106 andsubsequent data analysis by the additional data acquisition tool.Following step 770 (e.g., or step 780 and subsequent receipt of analyzeddata from a computational tool 104 or an additional data acquisitiontool 106 via interface module 140), analyzed data can be transmitted toapplication module 110 for display or to storage module 150 for storage.

The specific steps, their order, and the order of processes 300, 400,500, 600, and 700 may be defined by a stored or custom experiment designand/or by additional selections or preferences inputted by a user. Assuch, one or more of processes 300, 400, 500, 600, or 700 may compriseadditional steps, different steps, fewer steps, in accordance withembodiments of the systems, methods, and devices disclosed herein.

While preferred embodiments of the present invention have been shown anddescribed herein, it will be obvious to those skilled in the art thatsuch embodiments are provided by way of example only. Numerousvariations, changes, and substitutions will now occur to those skilledin the art without departing from the invention. It should be understoodthat various alternatives to the embodiments of the invention describedherein may be employed in practicing the invention. It is intended thatthe following claims define the scope of the invention and that methodsand structures within the scope of these claims and their equivalents becovered thereby.

1. A system for the classification of one or more specimen, the systemcomprising: a controller configured to: interface with one or moreinstrument through an instrument gateway module configured to receive aplurality of experimental data sets from the one or more instrument,wherein the plurality of experimental data sets is produced during aplurality of experiments; extract one or more feature data set from theplurality of experimental data sets; store at least a portion of the oneor more feature data set in a long-term data storage subsystem; store atleast a portion of the one or more feature data set or at least aportion of the plurality of experimental data sets in a short-termstorage cache; build one or more classification profile based on aclassification data set comprising at least a portion of the one or morefeature data set; and classify one or more specimen of an experiment ofthe plurality of experiments using the one or more classificationprofile, wherein the controller receives the plurality of experimentaldata sets before the classifying is performed on any of the experimentaldata sets.
 2. The system of any claim 1, wherein the classification dataset comprises at least a portion of each feature data set of a pluralityof feature data sets, wherein a first portion of the each feature dataset is produced from a first experimental data set of the plurality ofexperimental data sets and a second portion of the each feature data setis produced from a second experimental data set of the plurality ofexperimental data sets.
 3. The system of claim 2, wherein the firstexperimental data set comprises data from a different experiment of theone or more experiment plurality of experiments than the data of thesecond experimental data set, the plurality of experiments comprising100, 200, 500, 1,000, 5,000, 10,000, or 100,000 different experiments.4. The system of claim 1, wherein the controller receives the pluralityof experimental data sets before the extracting is performed on any ofthe experimental data sets.
 5. (canceled)
 6. The system of claim 2,wherein at least a portion of the first experimental data set isreceived from a different instrument of the one or more instrument thanthe second experimental data set.
 7. The system of claim 1, wherein theone or more specimen comprises 100, 150, 200, 500, 1,000, 2,500, 5,000,7,500, or 10,000 different specimen and the classification of the one ormore specimen comprises categorizing the one or more specimen based onone or more feature data set.
 8. The system of claim 1, wherein buildingthe classification profile comprises supervised machine learning orunsupervised machine learning. 9-10. (canceled)
 11. The system of claim1, wherein classification results are determined from the classificationof one or more specimen of an experiment of the plurality of experimentsusing the classification profile. 12-13. (canceled)
 14. The system ofclaim 1, wherein the controller is further configured to display ananalysis data set comprising at least a portion of the experimental datasets, at least a portion of the one or more feature data set, or atleast a portion of the classification data set, wherein the analysisdata set is displayed in real-time, near-real time, or batch mode.15-21. (canceled)
 22. The system of claim 1, wherein the one or morespecimen comprises one or more colony of microbial cells.
 23. (canceled)24. A method for the classification of one or more specimen, the methodcomprising: receiving a plurality of experimental data sets from one ormore instrument, wherein the plurality of experimental data sets isproduced during a plurality of experiments; extracting one or morefeature data set from the plurality of experimental data sets; storingat least a portion of the one or more feature data set in a long-termdata storage subsystem; storing at least a portion of the one or morefeature data set or at least a portion of the plurality of experimentaldata sets in a short-term storage cache; building one or moreclassification profile based on a classification data set comprising atleast a portion of the one or more feature data set; and classifying oneor more specimen of an experiment of plurality of experiments using theone or more classification profiles, wherein the plurality ofexperimental data sets is received before the classifying is performedon any of the experimental data sets.
 25. The method of claim 24,wherein the classification data set comprises at least a portion of eachfeature data set of a plurality of feature data sets, wherein a firstportion of the each feature data set is produced from a firstexperimental data set of the plurality of experimental data sets and asecond portion of the each feature data set is produced from a secondexperimental data set of the plurality of experimental data sets. 26.The method of claim 25, wherein the first experimental data setcomprises data from a different experiment of the plurality ofexperiments than the data of the second experimental data set, theplurality of experimental data sets comprising data from 100, 200, 500,1,000, 5,000, 10,000, or 100,000 experiments.
 27. The method of claim24, wherein the plurality of experimental data sets is received beforethe extracting is performed on any of the experimental data sets of theplurality of experimental data sets.
 28. (canceled)
 29. The method ofany claim 25, wherein at least a portion of the first experimental dataset is received from a different instrument of the one or moreinstrument than the second experimental data set.
 30. The method ofclaim 24, wherein the one or more specimen comprises 100, 150, 200, 500,1,000, 2,500, 5,000, 7,500, or 10,000 different specimen and theclassification of one or more specimen comprises categorizing the one ormore specimen based on one or more set of feature data.
 31. The methodof claim 24, wherein building the classification profile comprisessupervised machine learning or unsupervised machine learning. 32-33.(canceled)
 34. The method of claim 24, wherein classification resultsare determined from the classification of one or more specimen of anexperiment of the plurality of experiments using the classificationprofile. 35-36. (canceled)
 37. The method of claim 24, furthercomprising displaying an analysis data set comprising at least a portionof the plurality of experimental data sets, at least a portion of theone or more feature data set, or at least a portion of theclassification data set, wherein the analysis data set is displayed inreal-time, near-real time, or batch mode. 38-44. (canceled)
 45. Themethod of claim 24, wherein the one or more specimen comprises one ormore colony of microbial cells.
 46. (canceled)